| V-234218 | High | The FortiGate device must be configured to send log data to a central log server for the purpose of forwarding alerts to the administrators and the ISSO. | The aggregation of log data kept on a syslog server can be used to detect attacks and trigger an alert to the appropriate security personnel. The stored log data can be used to detect weaknesses... |
| V-234208 | High | The FortiGate device must use LDAPS for the LDAP connection. | Passwords need to be protected at all times, and encryption is the standard method for protecting passwords. If passwords are not encrypted, they can be plainly read (i.e., clear text) and easily... |
| V-234199 | High | The FortiGate device must prohibit the use of all unnecessary and/or non-secure functions, ports, protocols, and/or services. | To prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within data types), organizations must disable unused... |
| V-234212 | High | The FortiGate device must implement cryptographic mechanisms using a FIPS 140-2 approved algorithm to protect the confidentiality of remote maintenance sessions. | This requires the use of secure protocols instead of their unsecured counterparts, such as SSH instead of telnet, SCP instead of FTP, and HTTPS instead of HTTP. If unsecured protocols (lacking... |
| V-234211 | High | The FortiGate devices must use FIPS-validated Keyed-Hash Message Authentication Code (HMAC) to protect the integrity of nonlocal maintenance and diagnostic communications. | Unapproved mechanisms that are used for authentication to the cryptographic module are not verified and therefore cannot be relied upon to provide confidentiality or integrity, and DoD data may be... |
| V-234210 | High | The FortiGate device must use FIPS 140-2 approved algorithms for authentication to a cryptographic module. | Unapproved mechanisms that are used for authentication to the cryptographic module are not validated and therefore cannot be relied upon to provide confidentiality or integrity, and DoD data may... |
| V-234216 | High | The FortiGate device must only allow authorized administrators to view or change the device configuration, system files, and other files stored either in the device or on removable media (such as a flash drive). | This requirement is intended to address the confidentiality and integrity of system information at rest (e.g., network device rule sets) when it is located on a storage device within the network... |
| V-234214 | High | The FortiGate device must terminate idle sessions after 10 minutes of inactivity. | Terminating an idle session within a short time period reduces the window of opportunity for unauthorized personnel to take control of a management session enabled on the console or console port... |
| V-234193 | High | The FortiGate device must be running an operating system release that is currently supported by the vendor. | Network devices running an unsupported operating system lack current security fixes required to mitigate the risks associated with recent vulnerabilities. |
| V-234190 | Medium | The FortiGate device must limit privileges to change the software resident within software libraries. | Changes to any software components of the network device can have significant effects on the overall security of the network. Therefore, only qualified and authorized individuals should be allowed... |
| V-234191 | Medium | The FortiGate device must enforce access restrictions associated with changes to the system components. | Changes to the hardware or software components of the network device can have significant effects on the overall security of the network. Therefore, only qualified and authorized individuals... |
| V-234178 | Medium | The FortiGate device must generate audit records containing information that establishes the identity of any individual or process associated with the event. | Without information that establishes the identity of the subjects (i.e., administrators or processes acting on behalf of administrators) associated with the events, security personnel cannot... |
| V-234179 | Medium | The FortiGate device must generate audit records containing the full-text recording of privileged commands. | Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
Organizations consider limiting the additional audit information to only... |
| V-234194 | Medium | The FortiGate device must generate log records for a locally developed list of auditable events. | Auditing and logging are key components of any security architecture. Logging the actions of specific events provides a means to investigate an attack; to recognize resource utilization or... |
| V-234195 | Medium | The FortiGate device must conduct backups of system-level information contained in the information system when changes occur. | System-level information includes default and customized settings and security attributes, including ACLs that relate to the network device configuration, as well as software required for the... |
| V-234196 | Medium | The FortiGate device must support organizational requirements to conduct backups of information system documentation, including security-related documentation, when changes occur or weekly, whichever is sooner. | Information system backup is a critical step in maintaining data assurance and availability. Information system and security-related documentation contains information pertaining to system... |
| V-234197 | Medium | FortiGate devices performing maintenance functions must restrict use of these functions to authorized personnel only. | There are security-related issues arising from software brought into the network device specifically for diagnostic and repair actions (e.g., a software packet sniffer installed on a device to... |
| V-234172 | Medium | The FortiGate device must generate audit records when successful/unsuccessful attempts to modify administrator privileges occur. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident... |
| V-234173 | Medium | The FortiGate device must generate audit records when successful/unsuccessful attempts to delete administrator privileges occur. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident... |
| V-234170 | Medium | The FortiGate device must retain the Standard Mandatory DoD Notice and Consent Banner on the screen until the administrator acknowledges the usage conditions and takes explicit actions to log on for further access. | The banner must be acknowledged by the administrator prior to the device allowing the administrator access to the network device. This ensures the administrator has seen the message and accepted... |
| V-234171 | Medium | The FortiGate device must log all user activity. | This requirement supports non-repudiation of actions taken by an administrator and is required to maintain the integrity of the configuration management process. All configuration changes to the... |
| V-234176 | Medium | The FortiGate device must generate audit records showing starting and ending time for administrator access to the system. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident... |
| V-234177 | Medium | The FortiGate device must generate audit records when concurrent logons from different workstations occur. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident... |
| V-234174 | Medium | The FortiGate device must generate audit records when successful/unsuccessful logon attempts occur. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an... |
| V-234175 | Medium | The FortiGate device must generate audit records for privileged activities or other system-level access. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident... |
| V-234200 | Medium | The FortiGate device must implement replay-resistant authentication mechanisms for network access to privileged accounts. | A replay attack may enable an unauthorized user to gain access to the application. Authentication sessions between the authenticator and the application validating the user credentials must not be... |
| V-234201 | Medium | The FortiGate device must authenticate SNMP messages using a FIPS-validated Keyed-Hash Message Authentication Code (HMAC). | Without authenticating devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity. Bidirectional authentication provides stronger safeguards to validate... |
| V-234202 | Medium | The FortiGate device must authenticate Network Time Protocol (NTP) sources using authentication that is cryptographically based. | If NTP is not authenticated, an attacker can introduce a rogue NTP server. This rogue server can then be used to send incorrect time information to network devices, which will make log timestamps... |
| V-234166 | Medium | The FortiGate device must allow full access to only those individuals or roles designated by the ISSM. | A mechanism to detect and prevent unauthorized communication flow must be configured or provided as part of the system design. If management information flow is not enforced based on approved... |
| V-234204 | Medium | The FortiGate device must enforce password complexity by requiring that at least one uppercase character be used. | Use of a complex passwords helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in... |
| V-234205 | Medium | The FortiGate device must enforce password complexity by requiring that at least one lowercase character be used. | Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in... |
| V-234206 | Medium | The FortiGate device must enforce password complexity by requiring at least one numeric character be used. | Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in... |
| V-234207 | Medium | The FortiGate device must enforce password complexity by requiring that at least one special character be used. | Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in... |
| V-234209 | Medium | The FortiGate device must not have any default manufacturer passwords when deployed. | Network devices not protected with strong password schemes provide the opportunity for anyone to crack the password and gain access to the device, which can result in loss of availability,... |
| V-234198 | Medium | The FortiGate device must use DoD-approved Certificate Authorities (CAs) for public key certificates. | For user certificates, each organization obtains certificates from an approved, shared service provider, as required by OMB policy. For federal agencies operating a legacy public key... |
| V-234183 | Medium | The FortiGate device must synchronize internal information system clocks using redundant authoritative time sources. | The loss of connectivity to a particular authoritative time source will result in the loss of time synchronization (free-run mode) and increasingly inaccurate time stamps on audit events and other... |
| V-234182 | Medium | The FortiGate device must generate an immediate real-time alert of all audit failure events requiring real-time alerts. | It is critical for the appropriate personnel to be aware if a system is at risk of failing to process audit logs as required. Without a real-time alert, security personnel may be unaware of an... |
| V-234181 | Medium | The FortiGate device must off-load audit records on to a different system or media than the system being audited. | Information stored in one location is vulnerable to accidental or incidental deletion or alteration.
Offloading is a common process in information systems with limited audit storage capacity. |
| V-234180 | Medium | The FortiGate device must allocate audit record storage capacity in accordance with organization-defined audit record storage requirements. | To ensure network devices have a sufficient storage capacity in which to write the audit logs, they need to be able to allocate audit record storage capacity. The task of allocating audit record... |
| V-234169 | Medium | The FortiGate device must display the Standard Mandatory DoD Notice and Consent Banner before granting access to the device. | Display of the DoD-approved use notification before granting access to the network device ensures privacy and security notification verbiage used is consistent with applicable federal laws,... |
| V-234168 | Medium | The FortiGate device must enforce the limit of three consecutive invalid logon attempts, after which time it must lock out the user account from accessing the device for 15 minutes. | By limiting the number of failed login attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute-forcing, is reduced. |
| V-234185 | Medium | The FortiGate device must protect audit information from unauthorized deletion. | Audit information includes all information (e.g., audit records, audit settings, and audit reports) needed to successfully audit information system activity.
If audit data were to become... |
| V-234184 | Medium | The FortiGate device must record time stamps for audit records that can be mapped to Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT). | If time stamps are not consistently applied and there is no common time reference, it is difficult to perform forensic analysis.
Time stamps generated by the application include date and time.... |
| V-234165 | Medium | The FortiGate device must have only one local account to be used as the account of last resort in the event the authentication server is unavailable. | Authentication for administrative (privilege-level) access to the device is required at all times. An account can be created on the device's local database for use when the authentication server... |
| V-234164 | Medium | The FortiGate device must automatically audit account removal actions. | Account management, as a whole, ensures access to the network device is being controlled in a secure manner by granting access to only authorized personnel. Auditing account removal actions will... |
| V-234189 | Medium | The FortiGate device must enforce access restrictions associated with changes to device configuration. | Failure to provide logical access restrictions associated with changes to device configuration may have significant effects on the overall security of the system.
When dealing with access... |
| V-234188 | Medium | The FortiGate device must prohibit installation of software without explicit privileged status. | Allowing anyone to install software, without explicit privileges, creates the risk that untested or potentially malicious software will be installed on the system. This requirement applies to code... |
| V-234163 | Medium | The FortiGate device must automatically audit account modification. | Since the accounts in the network device are privileged or system-level accounts, account management is vital to the security of the network device. Account management by a designated authority... |
| V-234162 | Medium | The FortiGate device must automatically audit account creation. | Upon gaining access to a network device, an attacker will often first attempt to create a persistent method of reestablishing access. One way to accomplish this is to create a new account.... |
| V-234213 | Medium | The FortiGate device must terminate idle sessions after 10 minutes of inactivity. | If a device management session or connection remains open after management is completed, it may be hijacked by an attacker and used to compromise or damage the network device.
Nonlocal device... |
| V-234217 | Medium | The FortiGate device must protect against known types of denial-of-service (DoS) attacks by employing organization-defined security safeguards. | DoS prohibit a resource from being available for legitimate users. When this occurs, the organization either cannot accomplish its mission or must operate at degraded capacity.
This requirement... |
| V-234215 | Medium | The FortiGate device must generate unique session identifiers using a FIPS 140-2-approved random number generator. | Sequentially generated session IDs can be easily guessed by an attacker. Employing the concept of randomness in the generation of unique session identifiers helps to protect against brute-force... |
| V-234167 | Medium | The FortiGate device must audit the execution of privileged functions. | Misuse of privileged functions, either intentionally or unintentionally by authorized users, or by unauthorized external entities that have compromised information system accounts, is a serious... |
| V-234219 | Medium | The FortiGate device must limit the number of logon and user sessions. | Device management includes the ability to control the number of administrators and management sessions that manage a device. Limiting the number of allowed administrators and sessions per... |
| V-234221 | Medium | The FortiGate device must require that when a password is changed, the characters are changed in at least eight of the positions within the password. | If the application allows the user to consecutively reuse extensive portions of passwords, this increases the chances of password compromise by increasing the window of opportunity for attempts at... |
| V-234192 | Medium | The FortiGate device must use LDAP for authentication. | Centralized management of authentication settings increases the security of remote and nonlocal access methods. This control is particularly important protection against the insider threat. With... |
| V-234187 | Medium | The FortiGate device must protect audit tools from unauthorized modification. | Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on... |
| V-234220 | Medium | The FortiGate device must only install patches or updates that are validated by the vendor via digital signature or hash. | Changes to any software components can have significant effects on the overall security of the network device. Verifying software components have been digitally signed or hashed ensures that the... |
| V-234203 | Medium | The FortiGate device must enforce a minimum 15-character password length. | Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password length is one factor of several that helps to... |
| V-234186 | Medium | The FortiGate device must protect audit tools from unauthorized access. | Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on... |
